I'd say two things:

1. There should be some mention that if you are shipping a library of some sort that you need your build system to build both with and without PCH enabled so that you know if you have broken header requirements anywhere (since PCH essentially makes all of the common includes global to every single .cpp file in the project). This is something I've seen in the real world where a PCH build worked but a non-pch did not.
2. It might be worth mentioning that your build system might have some support for PCH, like the cmake add-in cotire

1.) That's a good point. I had some trouble with this in the past too. I will add something about the possible broken header requirements. This page summarizes some more drawbacks for precompiled headers usage in GCC: https://gcc.gnu.org/wiki/PCHHaters
Some of the points are valid for other compilers too.
2.) I did not know this tool, but it sounds interesting. Should definitely be worth mentioning.

I added some more informations to the disadvantages of precompiled headers and noted cotire. As always feel free to improve my English.